Configurations
Project-level configurations let you customize Change for your project. To see the configuration settings, go to project settings, and then select Change >Configurations.
ID customization
If projects are allowed to edit PCO or CCO IDs, (that is, the Allow projects to edit settings check box at the organization level is checked), you can override the organization-level numbering by setting the Generate Potential Change order IDs sequentially toggle to Yes. If set to No, IDs function as free text.
When the Generate Potential Change order IDs sequentially toggle is set to Yes, the Allow users to edit generated IDs toggle is shown, and the Prefix and Starting number fields are enabled. You can set the Allow users to edit Generated IDs to Yes to allow users to edit the generated IDs when creating a PCO or CCO or for a PCO or CCO that has been generated. When the field is set to No, users cannot edit the IDs and must use the IDs generated by Change.
You can edit the starting number field only if a PCO or CCO has not been created.
Pricing configuration
The Pricing configuration settings let you configure automatic pricing updates and VCO creation upon CCO execution.
You can specify whether edits to pricing automatically update between levels (for example, a change made at the client change order automatically updating the same line at the potential change order and issue levels).
The Pricing configuration page lets you indicate whether to automatically update to higher or lower levels.
When the Automatically update value changes to higher levels switch is set to Yes, the following updates are made:
-
Any changes made at the issue level are automatically reflected in the PCO and CCO.
-
Any changes made at the PCO level are automatically reflected in the CCO.
When the Automatically update value changes to higher levels switch is set to No, you can make the following manual changes:
-
At the issue level, you can push values to a PCO or CCO. If the PCO is associated with a CCO, the value is automatically pushed to the CCO.
-
At the PCO level, you can push values to a CCO or pull values from the issue.
-
At the CCO level, you can pull values from the issue or PCO. Values always pull from the issue through the PCO if associated.
When the Automatically update value changes to lower levels switch is set to Yes, the following updates are made:
-
Any changes made at the CCO level are automatically reflected in the PCO and issue.
-
Any changes made at the PCO level are automatically reflected in the issue.
When the Automatically update value changes to lover levels switch is set to No, you can make the following manual changes:
-
At the issue level, you can pull values from the PCO or CCO. Values always pull from the CCO to the PCO if the PCO is associated with the CCO.
-
At the PCO level, you can push values to the issue or pull values from the CCO.
-
At the CCO level, you can push values to the issue or PCO. Values will always push to the issue through the PCO if the PCO is associated with an issue.
Manual updates only push values down if they are edited on a lower level pricing item. For example, If you make a PCO-level pricing adjustment in a CCO, the value pushes down to the PCO and not the issue.
The Vendor change order configuration section lets you specify whether to automatically create a vendor change order (VCO) in InEight Contract from pricing items. When set to Yes, VCOs are automatically created from pricing items that are not already associated to a VCO upon execution of the CCO. When set to No, you must manually create the VCOs in Contract.
Pricing markup
The Pricing markups Configurations section is used to bring over markup values into the Pricing summary and cost item pricing.
You can configure a predefined set of markups and either have the markups automatically populate in the Pricing summary tab or Cost item pricing tab for an issue, or otherwise choose to select specific markups from a list set.
| Item Number | Field | Definition |
|---|---|---|
|
1 |
Markup Name |
Actual name of markup. |
|
2 |
Markup percentage |
Amount added to the cost price of goods or services to cover overhead and profit. Percentages can have up to three digits before the decimal. |
|
3 |
Applied to section |
The section that the markup applies to, which includes Labor, Equipment, Materials, Small tools & supplies, Self-perform subtotal, Vendor Subtotal, Time related overhead, and Grand total. |
|
4 |
Markup level | Markup calculation levels can be added to the Grand total in cost item pricing or to the Grand subtotal in the pricing summary. Levels 0-4 are available. Markups to other sections are automatically added at level 0. See Markup calculation levels for more information. |
|
5 |
Auto Display |
If set to Yes, the markup populates automatically under the Pricing summary column. If set to No, you have the option to bring in the markup, but the markup does not show automatically. |
Dependent cost items
The Dependent cost items Configurations section is used to bring dependent cost item values into cost item pricing.
You can configure a predefined set of dependent cost items, so you can select specific markups from a list set.
| Field | Description |
|---|---|
| Dependent cost item name | The name of the dependent cost item that will show in cost item pricing. |
| Cost percentage | The percentage to be multiplied by all items in the cost item pricing section to calculate the value of the dependent cost item. |
| WBS | The WBS code for the dependent cost item. |
| Applied to section | The section that the dependent cost item applies to, which includes Labor, Equipment, Materials, Small tools & supplies, Self-perform subtotal, Vendor Subtotal, Time related overhead, and Grand total. |
Decimal precision
You can use the Decimal precision configuration to set the number of digits that follow a decimal point. The precision decimals are used in issue, potential change order, and client change order logs, detail pages; and pricing. Exports for the logs also support decimal precision.
Tag output uses two decimal places.
You can choose separate decimal precision for values, quantities, and percentages.
You can choose 0-11 digits. If you choose 11 digits, the decimal characters do not fit in the fields of the issue, PCO and CCO headers, and an ellipsis is shown. If you do not enter a value, Change uses a default value of 2.
Message Configuration
Your organization has set defaults for scope status in the organization level settings. This helps drive business behavior or requiring messages for status charges. At the Project level settings, access from Project settings > Change > Configuration > Message configurations. From the Configuration list you can toggle on/off the display message, as well as allowing notes. The explanation icon depicts this line item is set at the organization level.
Responsible Party
Your organization can establish a default responsible party list in the organization settings. The project inherits the organization list and may mark some as inactive or create additional responsible party options.
To customize responsible party at a project level, go to Project settings > Change > Configurations.
The organization list defaults to active. To deactivate, change the toggle in the Action column from the check mark to the minus sign, and then save. Only those responsible party options with an active control are available to select in the issue, PCO, and CCO logs Responsible Party drop-down menus.
Construction Area for existing projects
In Change, for projects that started prior to Release 22.10, you have a drop-down list to reference Construction Areas to project changes you are tracking. In the Construction Area of Configurations, you can indicate where the drop-down list of Construction Area comes from.
On the Construction area section of this page, you can switch the toggle to select the source of the Construction Area attributes.
When the toggle is set to Yes, construction work area information configured in the InEight Platform Construction Work area (project > Project values > Area) populates the Construction area drop-down list in the Field information section of the Additional details in an issue.
When the toggle is set to No, you can enter construction area values, and those values populate the Construction area drop-down list. The Construction Area attributes are used in Change.
Construction area configuration in Change is not an option for projects that started with release 22.10 or later, the only way to customize Construction area information is in the Platform Construction area configuration.
Custom lists
Custom lists let you create fields with drop-down lists. Values configured for the custom lists automatically populate project drop-down lists in the specified order. To configure a custom list go to Project settings > Configurations > Custom Lists, and then select the custom list.
You can create two custom lists each for issues, PCOs, and CCOs. For each list item, you can add the list position and the description. When a list item is no longer needed for your project, you can switch the Active toggle to Off.
The custom lists are available in the Column options on the issue, PCO, and CCO logs, and you can change the values directly from the log. The fields are not available on the Details pages.
You can use custom labels (Project > Settings > Change > Custom Labels) to customize the names of the fields and lists.